Legacy network maximum transmission unit isolation capability through deployment of a flexible maximum transmission unit packet core design

ABSTRACT

Facilitating flexible maximum transmission unit packet core design in a communications network is provided herein. A system can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise receiving a first transmission unit setting from a first network device. The first transmission unit setting can indicate a size of a largest network layer protocol data unit that is able to be communicated in a single network transaction by the first network device. The operations can also comprise setting, at the device, a configuration of the first network device to the first transmission unit setting. Further, the operations can comprise sending first communication packets to the first network device using the first transmission unit setting and second communication packets to a second network device using a second transmission unit setting different from the first transmission unit setting.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 15/945,094 (now U.S. Pat. No.10,638,363), filed Apr. 4, 2018, and entitled “LEGACY NETWORK MAXIMUMTRANSMISSION UNIT ISOLATION CAPABILITY THROUGH DEPLOYMENT OF A FLEXIBLEMAXIMUM TRANSMISSION UNIT PACKET CORE DESIGN,” the entirety of whichapplication is hereby expressly incorporated by reference herein.

TECHNICAL FIELD

The subject disclosure relates generally to communications systems, and,for example, to maximum transmission unit packet core design incommunication networks.

BACKGROUND

In communication networks, the maximum transmission unit setting,particularly in the mobile packet core, has remained at a constant valueand, thus, has been implemented as a “one size fits all” approach. Forexample, the “one size fits all” approach for the maximum transmissionunit setting is applied to legacy communication networks and updatedcommunication networks that can support a higher maximum transmissionunit setting. Therefore, unique opportunities exist for application ofthe maximum transmission unit setting in an end-to-end network, whichcan comprise both legacy communication networks and updatedcommunication networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Various non-limiting embodiments are further described with reference tothe accompanying drawings in which:

FIG. 1 illustrates an example, non-limiting, network design;

FIG. 2 illustrates an example, non-limiting, network with a flexiblemaximum transmission unit packet core design in accordance with one ormore embodiments described herein;

FIG. 3 illustrates a structure of a general packet radio servicetunneling protocol user data tunneling header in accordance with one ormore embodiments described herein;

FIG. 4 illustrates an example, non-limiting, data structure of maximumtransmission unit signaling messages that can be utilized with thedisclosed aspects;

FIG. 5 illustrates an example, non-limiting, structure of a generalpacket radio service tunneling protocol user data tunneling header usingextension header in accordance with one or more embodiments describedherein;

FIG. 6 illustrates an outline of an extension header format inaccordance with one or more embodiments described herein;

FIG. 7 illustrates an example, non-limiting, logical maximumtransmission unit data structure that can associate respective maximumtransmission units with source internet protocol addresses in accordancewith one or more embodiments described herein;

FIG. 8 illustrates an example, non-limiting, maximum transmission unitdata structure that tracks maximum transmission unit network capabilityin accordance with one or more embodiments described herein;

FIG. 9 illustrates an example, non-limiting, representation of a radioaccess network access point that connects to multiple packet gateways inaccordance with one or more embodiments described herein;

FIG. 10 illustrates an example, non-limiting, signaling flow for aperiodic tracking area update in accordance with one or more embodimentsdescribed herein;

FIG. 11 illustrates an example, non-limiting, maximum transmission unitquarantine band network implementation in accordance with one or moreembodiments described herein;

FIG. 12 illustrates an example, non-limiting, method for utilization ofa flexible transmission unit packet core design in accordance with oneor more embodiments described herein;

FIG. 13 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein; and

FIG. 14 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein.

FIG. 15 is an example illustration of data indicating MTU Supportedinformation element identifier (IEI) and MTU Size.

DETAILED DESCRIPTION

One or more embodiments are now described more fully hereinafter withreference to the accompanying drawings in which example embodiments areshown. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the various embodiments. However, the variousembodiments can be practiced without these specific details (and withoutapplying to any particular network environment or standard).

Discussed herein are various aspects that relate to facilitatingflexible transmission unit settings. The transmission unit settings canbe maximum transmission unit (MTU) settings, which indicate the size ofthe largest network layer protocol data unit that can be communicated ina single network transaction. For example, legacy communication networkscan be configured to process a relatively low MTU setting value, such asa value of 1500 MTU, 1430 MTU, and so on. In contrast, newer or updatedportions of the networks can be configured to process either the samevalue as the legacy communication networks, or a higher MTU settingvalue, such as 2000 MTU, 2500 MTU, 9600 MTU, and so on. Thus, since thenewer or updated communication networks can be configured to process thehigher MTU setting value, such communication networks can utilize alarger packet size, which can decrease latency. Accordingly, the one ormore aspects discussed herein can be utilized to increase and optimizecommunication network (e.g., a General Packet Radio Service(GPRS_Tunneling Protocol (GTP) network) MTU settings.

According to some implementations, a single Internet Protocol (IP)address can have multiple MTU settings, depending on a source ordestination IP address. A Packet Gateway (PGW) can be configured withthis capability based on an MTU to IP address logic data structure. TheRadio Access Network (RAN) can communicate its MTU capability in realtime back to the PGW and the PGW can ensure that the logical MTU datastructure remains up to date with the most current information. When amobility session is established, the PGW can refer to the MTU datastructure and use the corresponding MTU size for the Gn/GP or S5/S8 orN3/N9 interface transport. A mobile device or user equipment (UE) canalso receive the optimal MTU setting from the PGW, based on the MTUcapabilities established in the logical MTU data structure.

Advantages of the various aspects provided herein, for layer 3 packettransport, can comprise: decreased latency, increased throughput, andincreased router capacity. These advantages can be driven by increasedlayer 3 packet sizes and reduced packet fragmentation on the Gn/GP orS5/S8 or N3/N9 transport. A 5G network, for example, can be heavilyinfluenced by latency. The current technological state of the art doesnot offer the degree of flexibility needed for the limited capabilitiesof legacy communication networks and the upgraded capabilities of newercommunication networks to coexist, without the legacy communicationnetworks holding down the newer communication networks. The variousaspects discussed herein provide a way for the MTU network parameters oflegacy communication networks to not hamper and hold back the MTUnetwork parameters of the newer communication networks. Thus, when moreadvanced packet networks are deployed, the core packet transportparameters can be easily established to support the less advancednetworks (e.g., the legacy communication networks) and the newercommunication networks at the same time. In addition, when upgrading thelegacy communication networks, the upgraded networks can be self-awareand can establish the optimal MTU settings for the overall network.Thereby network data packet throughput can increase, overall latency candecrease, and the routers that transport packets can have increasedcapacity.

In one embodiment, described herein is a system that can comprise aprocessor and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations. Theoperations can comprise receiving a first transmission unit setting froma first network device. The first transmission unit setting can indicatea size of a largest network layer protocol data unit that is able to becommunicated in a single network transaction by the first networkdevice. The operations can also comprise setting, at the device, aconfiguration of the first network device to the first transmission unitsetting. Further, the operations can comprise sending firstcommunication packets to the first network device using the firsttransmission unit setting and second communication packets to a secondnetwork device using a second transmission unit setting different fromthe first transmission unit setting. In an example, the firsttransmission unit setting can be different than a defined transmissionunit setting that is common to the first network device and the secondnetwork device (e.g., a 1500 MTU setting).

In another example, sending the first communication packets to the firstnetwork device can comprise fragmenting the first communication packetsto satisfy the first transmission unit setting. Further, sending thesecond communication packets to the second network device can comprisefragmenting the second communication packets to satisfy the secondtransmission unit setting.

According to an example, receiving the first transmission unit settingcan comprise receiving a broadcast message from the first networkdevice. The broadcast message can comprise a local source internetprotocol address of the first network device and can be transmitted to agroup of destination internet protocol addresses, comprising adestination internet protocol address of the device. Further to thisexample, the group of destination internet protocol addresses can beselected from a local database table (e.g., data structure) thatindicates recipients of the broadcast message. Further to this example,the operations can comprise removing the local source internet protocoladdress of the first network device from a transmission unit logic datastructure based on a determination that a defined time has elapsed sincereceipt of the first transmission unit setting from the first networkdevice.

In accordance with another example, the configuration of the firstnetwork device is a first configuration of the first network device andthe operations further comprise determining a third transmission unitsetting for a user equipment device serviced by the first networkdevice. The operations can also comprise facilitating a secondconfiguration of a transmission to the user equipment device based onthe third transmission unit setting. Further to this example,determining the third transmission unit setting can comprise determininga byte value associated with packet delivery limitations of a data planepath between the first network device and the user equipment device andreducing the first transmission unit setting by the byte value to derivethe third transmission unit setting. Alternatively, or additionally, theoperations can comprise updating the third transmission unit settingbased on a determination that the user equipment device has moved from afirst transmission unit zone associated with the first network device toa second transmission unit zone associated with a third network devicethat has a different transmission unit setting than the firsttransmission unit setting.

In an example, the first network device can be associated with a smallcell network. Further, the third transmission unit setting can bereduced to accommodate a transmission capability of the small cellnetwork.

According to an implementation, the first network device is a basestation device and the device is a packet gateway device. Further tothis implementation, receiving the first transmission unit setting fromthe first network device can comprise receiving the first transmissionunit setting from the base station device. Further, setting theconfiguration of the first network device can comprise dynamicallyupdating the packet gateway device based on the first transmission unitsetting from the base station device.

According to an additional or alternative implementation, the device isa packet gateway device and the first network device is a controllerdevice. Further to this implementation, receiving the first transmissionunit setting from the first network device comprises periodicallyreceiving a static file, from the controller device, that comprises thefirst transmission unit setting.

According to another embodiment, provided herein is a machine-readablestorage medium that comprises executable instructions that, whenexecuted by a processor of a network device of a wireless network,facilitate performance of operations. The operations can comprisereceiving, from a first network device, a first signal that comprises afirst value that represents a first transmission unit setting supportedby the first network device and receiving, from a second network device,a second signal that comprises a second value that represents a secondtransmission unit setting supported by the second network device. Thesecond value can be different from the first value. The operations canalso comprise facilitating a first transmission of a first group ofpackets to the first network device based on the first value and asecond transmission of a second group of packets to the second networkdevice based on the second value.

In an example, the operations can also comprise receiving the firstsignal in a general packet radio service tunneling protocol user datatunneling header that comprises an extension header.

In another example, the operations can comprise determining a thirdvalue of a third transmission unit setting for a mobile device incommunication with the first network device. The third value can be lessthan the first value. The operations can also comprise facilitatingtransmission of an indication, to the first network device, thatcomprises the third value and information indicative of an identity ofthe mobile device. Further to this example, the operations can comprisedetermining a byte value associated with packet delivery limitations ofa data plane path between the first network device and the mobile deviceand reducing the first value by the byte value to derive the thirdvalue.

In further detail, FIG. 1 illustrates an example, non-limiting, networkdesign 100. In accordance with conventional technology the GTP (trusted)side of a mobility network operates as an enhanced packet core totransport and connect mobile device data to the internet (untrusted)content servers in order for users, through their respective devices(e.g., mobile devices or UE) to access World Wide Web (WWW) content, toaccess private company enterprise data center content, and/or to accessother content. As such, there are a variety of elements or parts (e.g.,routers, switches, mobile radio access points, packet gateways, and soon) that comprise the trusted side of the content delivery path. A setof these elements or parts can be new (with new or updated technology)and another set of these elements can be old (with old or outdatedtechnology). The various aspects provided herein can facilitatemodernizing and/or upgrading portions of the GTP network, whilemaintaining in place the various elements of the legacy network. In someinstances, portions of the legacy network, can be difficult, orimpossible, to upgrade. However, the aspects provided herein canfacilitate maximizing the speed of content delivery and reduce latency,where old and new elements or parts exist and are expected to coexisttogether.

According to an implementation, a flexible MTU network design isprovided. The Ethernet layer 2 and IP layer 3 MTU sizes are integralcomponents to Enhanced Packet Core (EPC) and 5G Packet Core (5GC) designthat affect throughput and latency. If the packet size allowed by theMTU is too small, then the number of data packets is increased, andoverall data throughput is decreased. Older networks, due to thecapabilities of older hardware, could typically have lower MTU thannewer networks which can support jumbo frames (e.g., packet sizes thatare greater than 1500 bytes and up to, and including, 9600 bytes).

In the conventional GTP network design, which many GTP data networksadhere to, the MTU setting is fixed to one value on centralized routerssuch as the Packet Gateway (PGW). Thus, the PGW is set to the MTU valueof the lowest MTU network component of the entire end-to-end network.For example, in a very large mobility network, the layer 2 ethernet MTUcapabilities, which are typically in the older parts of some geographiclocations, dictate the MTU settings on the eNB Radio Access Network(RAN) and PGW network equipment, even though the eNB and PGWs cansupport jumbo frame settings. Even though some more recently developedethernet switches, can support jumbo frames, the eNB and PGW cannot takeadvantage of this, and should set their MTU to the lowest MTU valueprovisioned on the oldest ethernet switches deployed.

With continuing reference to FIG. 1, in this example network 100 design,the network is limited to an MTU value of 1500. For example, a firstethernet switch 102 is deployed in a first geographic area (e.g.,Alaska), illustrated as a first eNB 104, and reaches a Packet Gateway orPGW 106 in a second geographic area (e.g., Seattle). In this example,the first ethernet switch 102 has an MTU value of 1500 (e.g., 1500 MTU).As illustrated, the network traffic can also go through a servinggateway 108, which can be in a different location than the PGW 106.However, in accordance with some implementations, the PGW and the SGWcan be co-located on a single device.

A second ethernet switch 110, which can be located in a third geographicarea (e.g., San Francisco), illustrated as a second eNB 112, and reachesthe PGW 106 in the second geographic area. In this example, the secondethernet switch 110 has an MTU value of 2000 (e.g., 2000 MTU). Althoughthe second ethernet switch 110 has a higher MTU value, the PGW 106 isstill set to 1500 MTU, which is the lowest common MTU setting of theentire network. The MTU setting on the PGW 106 is not aware of what MTUsettings are on the ethernet switches (e.g., the first ethernet switch102 and the second ethernet switch 110) because the MTU settings arestatically configured (set once and can only be changed manually) on thenetwork. For example, a command line interface it utilized to set theMTU size or value. The MTU size can be set on the user plane and,further, the RAN has a similar MTU command. In conventional systems, thePGW can be provisioned with an MTU size from 1500 to 2000. Similarly, onthe RAN, the UE can be configured with an MTU size from 1430 to 2000and, usually, is lower than the size of the data plane. Therefore, ifthe data plane has an MTU size of 1500, the UE can be given an MTU sizeof 1430, which is 70 bytes lower than the data plane. The 70 bytes canaccount for overhead that is utilized to transmit communications to theUE. By provisioning the UE for a lower MTU size, it can mitigate orreduce the number of packets that need to be fragmented.

To overcome the above noted situation, the various aspects providedherein allow for dynamic configuration of MTU settings. Therefore, aswill be discussed in further detail below, changes can be madecontinuously, continually, or based on other parameters. Based on thesechanges, the network can be automatically updated without manualintervention.

In some cases, dynamic changes of MTU settings have been attemptedthrough the use of the IP path discovery protocol, which can beproblematic in practice. For example, not every piece of networkequipment supports IP path discovery, and the messages can be subject tobeing blocked on firewalls. Also, the dynamic nature of IP pathdiscovery protocol can take a high toll on central processing unit (CPU)and software programing complexity, due to its dynamic nature. This canincrease the financial cost so extensively, that in many cases IP pathdiscovery is not supported on the GTP portion of networks. It is notedthat various aspects provided herein do not use any portion of the logicdeployed in IP path discovery protocol and do not rely on it as part ofthe solution.

As discussed herein, a hybrid method of static MTU settings can beimplemented on the Ethernet and eNB RAN equipment along with a dynamicMTU capability on the PGW. Thus, the various aspects are not limited toonly a mobility network architecture (eNB to PGW) but can be used inother network architecture implementations. However, for the purposes ofexplaining the various aspects, a mobility example will be used toillustrate and describe the basic concepts. This solution uniquelyallows a single IP address to have multiple MTU settings, which has notbeen previously accomplished.

FIG. 2 illustrates an example, non-limiting, network 200 with a flexiblemaximum transmission unit packet core design in accordance with one ormore embodiments described herein. Repetitive description of likeelements employed in other embodiments described herein is omitted forsake of brevity.

As discussed herein, a static MTU setting on the eNB (e.g., the firsteNB 104, the second eNB 112), reflects knowledge of the MTU capabilitiesof the Layer 2 ethernet switches that serve its packet transport. Thatstatic setting can be received by the PGW 106, such as over GTP generalpacket radio service tunneling protocol (GTP) encapsulated transport.Based on receipt of the static setting, the PGW 106 can dynamicallyreact to the MTU being advertised to it. Thus, the PGW 106 can set thePGW MTU to the optimal value serving that market.

For example, as illustrated in FIG. 2, the PGW MTU setting for the S1-Utunnel 202 that goes to the first geographic location (e.g., the firstethernet switch 102 and first eNB 104) can be set for 1500 bytes.Further, the PGW MTU setting for the S1-U tunnel 204 that goes to thethird geographic location (e.g., the second ethernet switch 110 andsecond eNB 112) can be set to 2000 bytes. This can allow users in thesecond location (with the upgraded elements) to have increased datathroughput and reduced latency. Prior to the changes stated above, andfurther described herein, the third geographic location would have tohave been served by a common, static MTU setting of 1500 on the PGW 106,and thus experience reduced overall network MTU until such time that theMTU at the first geographic location could be increased to 2000, atwhich point the network wide MTU setting on the PGW 106 could be changedfrom 1500 to 2000 bytes.

It is also noted that the settings on UEs at the first geographiclocation and the third geographic location could be set to a value thatis lower than the value of the first eNB 104 and the second eNB 112,respectively. In an example, one or more UEs 206 at the first geographiclocation could be set to a first value, such as MTU 1430, which providesfor 70 for overhead (e.g., MTU 1500 at the first eNB 102, less 70).Further to this example, one or more UEs 208 at the third geographiclocation could be set to a second value, such as 1930, which provides 70for overhead (e.g., MTU 2000 at the second eNB 112, less 70).

The one or more UEs 206, 208 can be customer location equipment, whichcan be equipment that is located at the customer location. The equipmentcould either be owned by the customer and/or by the network provider.Equipment can comprise, but is not limited to, cable television set topboxes, personal computers, IP and asynchronous transfer mode (ATM)routers, integrated access devices, mobile devices, wirelesscommunication devices, Digital Subscriber Line (DSL), cable, and otherhigh-speed modems.

Various aspects provided herein demonstrate a hybrid approach to havestatic MTU endpoints (eNB and/or other network equipment) communicateback to a dynamic MTU capable router (PGW and/or other networkequipment). Network equipment is equipment that is located at thenetwork provider location. The network equipment could either be ownedby the customer and/or by the network provider. Network equipment cancomprise, but is not limited to, eNB, ethernet switches, IP routers, andserving and packet gateways.

According to an implementation, multiple MTU settings can be allowed ona single source IP address. According to an alternative, or additional,implementation, “MTU advertising” of a source IP address MTU setting todestination IP addresses can be allowed. The source IP address candecide to advertise its MTU setting to all destination IP addresses, ora select few destination IP addresses, based on a local data structurethat determines which destination IP addresses should receive the MTUmessages.

The following provides a demonstration of a practical implementation ofthis concept by using GTP encapsulation protocol overhead settings.However, it is noted that the various aspects can also be used withother data protocols, or other encapsulation methods, provided theoverhead is modified and designed to support the concepts discussedherein.

An eNB traditionally communicates to a PGW using the GTP protocolthrough a packet data network designed for S5/S8 transport. Theconventional GTP protocol overhead, as defined by the 3GPPspecification, and implemented by many mobility network carriers, isdepicted in FIG. 3, which illustrates a 3GPP structure 300 of GTP-Uheader.

The 3GPP structure 300 can comprise a general packet radio servicetunneling protocol user data tunneling header or GTP-U header 302, whichcan be a variable length header whose minimum length is 8 bytes. TheGTP-U header 302 can comprise a version field 304 (used to determine theversion of the GTP-U protocol), a Protocol Type or PT field 306, areserved field 308, an extension header or E flag 310 (used to signalthe presence of the Extension Header field), a sequence number flag or Sflag 312 (used to signal the presence of the GTP Sequence Number field),and a N-PDU number flag or PN flag 314 (used to signal the presence ofN-PDU Numbers).

The octets 316 indicate the length of the payload (e.g., the balance ofthe packet following the mandatory portion of the GTP header (e.g., thefirst 8 octets)). A message type field 318 indicates the type of GTP-Umessage. Also illustrated are four tunnel endpoint identifiers (TEIDs),namely TEID (first Octect) 320, TEID (second Octect) 322, TEID (thirdOctect) 324, and TEID (fourth Octect) 326. The TEID unambiguouslyidentifies a tunnel endpoint in the receiving GTP-U protocol entity.

As illustrated, in Octet 2 there exists a message type that providesinstruction for the network equipment related to how to set up varioussignaling (control plane) messages across the user plane (data plane)tunnel, setup of the user plane tunnel, and user data plane messages.The 8-bit value present in the message type defines what the GTP-Upacket will be used for. As an example, message type 255 can indicatethe packets are to be used for standard user plane messages (G-PDU),while message type 26 can be used for error indications, message type 31can be used to indicate an extension of the GTP-U protocol, messages 16and 17 can be used for creating PDP contexts, and messages 1 and 2 canbe used for echo request and response. This large suite of messages isdefined in several 3GPP standards, including, for example, TS 29.281, TS29.060, and TS 32.295. It is noted that although specific message typesare discussed, the disclosed aspects are not limited to these specificmessage types and other message types can be utilized with the disclosedaspects.

It is noted that for the various aspects discussed herein, not allmessages are currently defined in 3GPP and are reserved for future use.As an example of an illustration of the concept described herein, theunused Messages Type(s) 106 to 110 are proposed for use with thedisclosed aspects. These five messages can be used as “MTU ControlMessages” in order to send the MTU size from the RAN (eNB) to the EPC(PGW) and thereby identify the specific MTU a RAN access network cansupport. For example, FIG. 4 illustrates an example, non-limiting, datastructure 400 of MTU signaling messages that can be utilized with thedisclosed aspects.

As illustrated, the data structure 400 can comprise a message type valuefield 402 (which can be expressed in decimals) and a message field 404.A message type 106 can indicate a MTU size of 1430 (which can bettersupport micro cells that use additional overhead for ESP encapsulation),message type 107 can indicate a MTU size of 1500, message type 108 canindicate a MTU size of 1600, message type 109 can indicate MTU sizes of2000, and message type 110 can indicate a MTU size of 9600.

It is noted that the various aspects provided herein are not limited tothese particular message type values 402 and messages 404, which aresolely provided for purposes of explaining the disclosed aspects.According to some implementations, less than five messages or more thanfive messages can be utilized. However, it is noted that five messagescan provide sufficient coverage for quarantining legacy MTU networks,emancipating current network equipment capabilities (as will bediscussed with respect to FIG. 11 below), and allowing for future MTUevolution. It can also resolve various challenges experienced in microsmall cell RAN, with excessive packet fragmentation caused by the use of70 additional bytes used for Encapsulating Security Payload (ESP)security encapsulation.

As an example of the use of the MTU control messages described herein,in FIG. 2, the first geographic location (e.g., Alaska) could send aGTP-U message for 107, periodically or based on another time interval,or as a follow up to the creation of a TEID user plane tunnel, e.g., ifthe eNB and associated Ethernet backhaul can only support 1500 bytepackets. Similarly, the third geographic location (e.g., San Francisco)could send GTP-U message 109, periodically or based on another timeinterval, or as a follow up to the creation of a TEID user plan tunnel,e.g., if the eNB and associated Ethernet backhaul can only support 2000byte packets.

To periodically (or based on another time interval) send the Message/MTUsize allows the eNB to put in a new MTU size later when the Layer 2Ethernet Backhaul or small cell back haul can support a higher MTU. Inthis case, the PGW can receive the MTU update automatically, and updatethe MTU data structure retained by the PGW accordingly.

The Packet Gateway (PGW) can have a logical MTU index data structure,whereby the PGW can keep track of which RAN (eNB) can support whatspecific MTU size. The PGW can therefore, send only packets of the sizethat the RAN can support, and not any larger. This capability can reducepacket fragmentation and can reduce packet latency, thus leading tofaster World Wide Web (WWW) browsing, or otherwise faster data transferwith increased packet size. According to some implementations, the PGWcan auto summary the IP address in order to reduce the size of thelogical MTU index data structure, which can become quite large,especially when small cells are included.

Other delivery methods of the MTU, using GTP, are possible other thanthe one described in detail thus far. An example of this is using theGTP extension header. FIG. 5 illustrates an example, non-limiting,structure of a GTP-U header using extension header in accordance withone or more embodiments described herein. Repetitive description of likeelements employed in other embodiments described herein is omitted forsake of brevity.

As illustrated in FIG. 5, when using the extension header, the third bitof Octet 1 (e.g., the E flag 502) can be set to “1”. This is per the3GPP TS 29.281 standard. The third bit of Octet 1 informs the downstreamGTP receiver that the extension header is being used. The local transmitMTU value would then have to be contained in the extension headercontent, in Octet 2-m, as depicted in FIG. 6, which illustrates anoutline of an extension header format 600 in accordance with one or moreembodiments described herein. As illustrated, the extension headerformat 600 can comprise an extension header length 602, an extensionheader content 604, and a next extension header type 606. The extensionheader content 604 could be as simple as a string that indicates “MTU is1500”, but, in implementation, could be more complicated.

Implementation of the extension header content method adds additionalbytes to the GTP tunnel overhead and is a possible MTU delivery method.This could be implemented if potential problems are encountered with theMTU signaling message. However, it is noted that the MTU signalingmessage method does not increase the GTP overhead that is currently inuse.

FIG. 7 illustrates an example, non-limiting, logical maximumtransmission unit data structure 700 that can associate respectivemaximum transmission units with source internet protocol addresses inaccordance with one or more embodiments described herein. Repetitivedescription of like elements employed in other embodiments describedherein is omitted for sake of brevity.

Illustrated in the first column 702 are eNB source IP addresses and inthe second column 704 are respective MTU sizes. In this case, the PGWreceives the eNB, or micro cell, MTU control message and correlates themto the source IP of the RAN. Thereby a PGW logical MTU data structurecan be constructed that comprises details related to what MTU should beassigned for any date traffic going to any RAN IP address. This conceptallows for one IP address to have multiple MTU settings. Thereby old andnew networks can be served with the optimal MTU settings needed foroptimal data transport.

With the PGW having a logical MTU data structure, it can further allowthe PGW to establish and send an optimal MTU setting to a User Equipment(UE). This also has added benefit for reducing packet fragmentation andthereby decreasing latency. The MTU size could be correctly sized forthe RAN market in which the user (e.g., the UE) is authenticated. Thiscan be accomplished by using protocol configuration options (PCOs) thatthe PGW uses in the Create Session Request (CSR) that provides a UE withinformation related to what MTU setting the UE should use for theduration of a session. For example, using FIG. 2, the PGW 106 caninstruct the UE to use 1430 in Alaska, and 1930 in San Francisco (e.g.,as the UE changes its location). Since the worst case GTP overhead isless than 70 bytes, using IPv6 transport, the UE can be using themaximum packet size that is possible for the RAN (eNB) serving it.

RAN can have increased overhead, when employing additional encryptedsecurity encapsulation, such as for micro cells where the packetbackhaul usually occurs over 1500 layer 3 MTU networks. Theseapplications can have less than 70 additional bytes of overhead that isneeded for the ESP security encapsulation. In this particular case, thePGW can be also capable of taking that additional ESP overhead intoaccount. For example, a micro cell can set its MTU to 1430, to reflectthe 70 bytes of ESP overhead needed, and the PGW can send any UEattaching to it, via the PCO option, a UE MTU size of 1360 (e.g., 1430minus the 70 bytes used for S5/S8 transport overhead). This can increasedata throughput and reduce latency for all UEs being served in a microcell environment.

The MTU control messages can be sent from the RAN (micro cells and eNB)to the centralized router (PGW) at periodic intervals. For example, onan hourly basis or at another interval. As the access network evolvesand the eNB access network can support a higher MTU setting, the eNB canre-provision the MTU setting to the higher value and the PGW canautomatically detect and use the increased MTU setting the next time thecontrol message is sent.

According to some implementations, an alternative method of a PGW MTUdata structure can include using the TEID of the S1-U tunnel. FIG. 8demonstrates this approach and illustrates an example, non-limiting, MTUdata structure 800 that tracks MTU network capability in accordance withone or more embodiments described herein. The MTU data structure 800comprises a first column for a tunnel endpoint identifier or TEID 802and a second column for the MTU size 804 corresponding to the TEID.

Each mobility session can be associated with a TEID used on the S1-Utunnel. This can be used to correlate the eNB MTU value to the PGWsession serving it. Here, the eNB can send the MTU signaling message tothe PGW as a follow up to any new session created with a TEID.

In this approach, as well, MTU can be automatically updated if the RANprovisions new MTU values. The MTU control message can simply containthe new MTU values that are sent as part of the establishment of theS1-U TEID. Using the IPv6 address of the eNB can be utilized and wouldnot require an existing S1-U tunnel between the eNB and PGW.

According to additional or alternative implementations, other optionsare also available to create an IP interface that has multiple MTUsettings based on source and/or destination IP address. In accordancewith a first example is an implementation where the eNB RAN IP providesits MTU to the PGW IP address via GTP messages. The allowed creation ofa PGW MTU data structure that could associate its destination IP addresswith the MTU of that specific RAN AP.

According to a second example, a master software program can be awareof, and can be kept up to date, with the packet size capabilities of theentire network. This software controller, such as ECOMP (EnhancedControl, Orchestration, Management and Policy) or controller device, canprovide a static MTU map to a master router, such as a PGW, in a fileformat, whereby the PGW implements this file as its logical MTU datastructure. As the network MTU capabilities evolve, then a new file issent from ECOMP to the PGW. This is an example of a static update to thePGW, if it occurred at fixed intervals. If ECOMP pushed a new MTU datastructure to the PGW, in real time, as network packet size (MTUcapabilities) changes are made, then this would be an example of adynamic PGW update. The difference between the two implementationexamples (the first example and the second example), is that in thefirst example, the local IP destination endpoints are providing the MTUinformation and updates to the central PGW, whereby each endpoint isinstructing the PGW. In the second example, a centralized controller, ororchestrator, entity is providing the update. As such, it is one entity,rather than the many entities that are used in the first example. Thevarious aspects provided herein can be utilized with variousimplementations, as demonstrated in the first example and the secondexample, such that a single IP interface can be aware of multiple MTUsettings based on prior knowledge of a networks packet deliverycapability.

Yet, another implementation of passing the edge networks MTU value, forexample from an eNB, MTU back to a centralized router, for example aPGW, can rely on using a control plane to relay the message. A benefitof this approach can be to send MTU updates back to the PGW, in afaster, and more organized manner, which could better cover mobilityevents.

Since there are typically more network elements involved in the transferof a GTP-C message in a mobility network (eNB, MME, PGW), implementationcan be costlier and time consuming. In addition, the details of thestructure of the GTP-C control message would be utilized. Traditionally,new elements are contained in an “Information Element” (IE). Therefore,an implementation of a flexible MTU design can be to pass the eNB MTUvalue as part of an IE, during a mobility session attach, or Inter RadioExchange (IRAT) hand off, through an MME, to the PGW. Thus, the PGW canbecome aware of the MTU value that the session can support. The PGW canthus be sent the most optimized MTU value (for example the MTU providedby the eNB minus the 70 bytes needed for GTP overhead), to a mobilephone. Thus, the MTU value for the network can be optimal and can reduceoverall latency, increase throughput, and optimize router packettransfers through reduced packet fragmentation.

A further implementation can be to send the UE MTU updates as the UEgoes through various parts of the legacy and modern (emancipated)network through radio exchange of the radio Access Points (AP) viaIRATs. This can provide real time MTU updates. In this approach, thecontrol plane can be establishing the MTU of the Data Plane (S1-U).

In an example, the existing 3GPP TS23.401 attach call flows do notchange. For example, for a 4G attach, the TS23.401 flow can still apply.The difference is that the new MTU IE is now handed off during step 2from the eNodeB to the MME, which comprises the new MTU IE handoff tothe Serving GW and PDN SGW (e.g., in steps 12 and 13 of the TS23.401flow). The PGW may send a different MTU PCO value in step 16 of theTS23.401 flow (Create Session Response), based on the MTU knowledge itobtained in step 13 of the TS23.401 flow (Create Session Request). Thisallows for MTU to be optimized end-to-end.

For the data plane S1-U implementation of MTU control messages, the PGWto RAN AP logical MTU data structure can have a time out value ofoptional setting. An example of this would be if no MTU control messageis received by the PGW in a defined interval (e.g., a twenty-four-hourperiod), the source AP IP address and associated MTU entry can beremoved from the logic data structure.

According to an implementation, a RAN AP does not have a list of PGWs itcan connect to. Instead, the RAN IP discovers the PGWs as mobilesessions are established. In the network, there are multiple PGWs thatan individual RAN AP can connect to. FIG. 9 illustrates an example,non-limiting, representation of a radio access network access point thatconnects to multiple packet gateways in accordance with one or moreembodiments described herein. Repetitive description of like elementsemployed in other embodiments described herein is omitted for sake ofbrevity.

As illustrated, the first ethernet switch 102 (in a first geographicarea, such as Alaska) can connect to various SGWs and PGWs. Asillustrated, a first connection can be to SGW 108 and PGW 106 in asecond geographic area (e.g., Seattle). A second connection can be to asecond PGW 902 and second SGW 904 in a third geographic location (e.g.,San Francisco). Further, a third connection (e.g., a new connection) canbe established to a third PGW 906 (e.g., a new PGW) and a third SGW 908(e.g., new SGW) located in a new or fourth geographic area (e.g.,British Columbia). For the first call from a RAN AP to a third PGW 906,the third PGW 906 will not know what MTU to assign the S1-U tunnel orthe mobile phone, since it will not have an entry yet for the source IPaddress in the PGW logical MTU data structure. (e.g., it will not havereceived an MTU control message since the RAN APN is unaware of the PGWIP address). In this case, if no IP address exists in the datastructure, the PGW can assign a default value of 1500 for the S1-Utunnel MTU. The RAN AP can retain a data structure of all the PGWsdetermined to exist in the network and can access that list on theperiodic interval defined, in order to send each PGW the MTU controlmessage.

The following discusses MTU updates during a tracking area update. Asolution to the “handover” problem from an eNB with jumbo MTU support toan eNB without (assuming they are in different tracking areas) caninvolve an indication of the supported MTU from the new eNB to the MMEin the Tracking Area Update (TAU) request. The MME could then send amodify bearer request with a new information element value that informsthe SGW and PGW of the new MTU and allows the PGW to adjust the size ifnecessary.

FIG. 10 illustrates an example, non-limiting, signaling flow 1000 for aperiodic tracking area update in accordance with one or more embodimentsdescribed herein. It is noted that this signaling flow 1000 can alsoapply to any TAU with no MME or SGW change. Illustrated arerepresentations of a UE 1002, an eNodeB 1004, an MME 1006, a servinggateway 1008, a PDN gateway 1010, a PCRF 1012, and a HSS 1014.

A tracking area update (TAU) request 1016 can be sent from the UE 1002to the eNodeB 1004 and forwarded to the MME 1006.Authentication/security 1018 can be performed based on the TAU request1016. A modify bearer request 1018 can be sent from the MME 1006 to theserving gateway 1008 and forwarded to the PDN gateway 1002. The PDNgateway 1002 can respond with a modify bearer response 1020, which canbe forwarded to the MME 1006. Thereafter, a TAU accept message 1022 canbe transferred from the MME 1006 to the UE 1002, through the eNodeB1004. Then an indication of completion of the tracking area update 1024can be transmitted from the UE 1002 to the MME 1006. (A more completedescription can be found in Section 5.3.3.2 in 3GPP TS 23.401 version15.1 “Tracking Area Update Process”).

According to the various aspects provided herein, the flow of FIG. 10can be modified to comprise the eNodeB forwarding the TAU request to theMME, as indicated at 1026. The TAU contents can be defined as indicatedin 3GPP TS 24.301, according to some implementations.

Table 1 below provides example, non-limiting, tracking area updaterequest message content according to one or more embodiments providedherein. As indicated in Table 1, according to one or more aspects, a newinformation element (IE) called “MTU Supported” can be inserted as anOptional IE in the TAU Request to the MME.

TABLE 1 IEI Information Element Type/Reference Presence Format LengthProtocol discriminator Protocol discriminator M V 1/2 9.2 Securityheader type Security header type M V 1/2 9.3.1 Tracking area updateMessage type M V 1 request message 9.8 identity EPS update type EPSupdate type M V 1/2 9.9.3.14 NAS key set identifier NAS key setidentifier M V 1/2 9.9.3.21 Old GUTI EPS mobile identity M LV 12 9.9.3.12 B- Non-current native NAS key set identifier O TV 1 NAS key setidentifier 9.9.3.21  8- GPRS ciphering key Ciphering key sequence O TV 1sequence number number 9.9.3.4a 19 Old P-TMSI signature P-TMSI signatureO TV 4 9.9.3.26 50 Additional GUTI EPS mobile identity O TLV 13 9.9.3.12 55 Nonce_(UE) Nonce O TV 5 9.9.3.25 58 UE network UE networkcapability O TLV 4-15 capability 9.9.3.34 52 Last visited registeredTracking area identity O TV 6 TAI 9.9.3.32  5C DRX parameter DRXparameter O TV 3 9.9.3.8 A- UE radio capability UE radio capability O TV1 information update information update needed needed 9.9.3.35 57 EPSbearer context EPS bearer context status O TLV 4 status 9.9.2.1 31 MSnetwork MS network capability O TLV 4-10 capability 9.9.3.20 13 Oldlocation area Location area O TV 6 identification identification 9.9.2.2 9- TMSI status TMSI status O TV 1 9.9.3.31 11 Mobile station Mobilestation classmark 2 O TLV 5 classmark 2 9.9.2.4 20 Mobile station Mobilestation classmark 3 O TLV 2-34 classmark 3 9.9.2.5 40 Supported CodecsSupported Codec List O TLV 5-n  9.9.2.10 F- Additional update Additionalupdate type O TV 1 type 9.9.3.0B  5D Voice domain Voice domainpreference O TLV 3 preference and UE's and UE's usage setting usagesetting 9.9.3.44 E- Old GUTI type GUTI type O TV 1 9.9.3.45 D- Deviceproperties Device properties O TV 1 9.9.2.0A C- MS network feature MSnetwork feature support O TV 1 support 9.9.3.20A 10 TMSI based NRINetwork resource O TLV 4 container identifier container 9.9.3.24A  6AT3324 value GPRS timer O TLV 3 2 9.9.3.16  5E T3412 extended value GPRStimer O TLV 3 3 9.9.3.16B  6E Extended DRX Extended DRX parameters O TLV3 parameters 9.9.3.46 ?? MTU Supported See below O TV 1

FIG. 15 is an example illustration of data indicating MTU Supported IEIand MTU Size. The MTU Size values can range from 0 to 15. For example,the size and values are indicated in Table 2 below.

TABLE 2 Size Values 0 (default) 1500 1 1430 2 1600 3 2000 4 9600 5-15Future Use

The MME can then send a modify bearer request to the S/PGW (Step 9). TheIEs included are as indicated in Table 3 below:

TABLE 3 Information elements P Condition/Comment IE Type Ins. MEIdentity C This IE shall be sent on the S5/S8 interfaces for MEI 0 (MEI)the Gn/Gp SGSN to MME TAU. User Location C The MME/SGSN shall includethis IE for ULI 0 Information TAU/RAU/Handover procedures if the PGW(ULI) has requested location information change reporting and MME/SGSNsupport location information change reporting. An MME/SGSN whichsupports location information change shall include this IE forUE-initiated Service Request procedure if the PGW has requested locationinformation change reporting and the UE's location info has changed. TheSGW shall include this IE on S5/S8 if it receives the ULI from MME/SGSN.C This IE shall also be included on the S4/S11 O interface for aTAU/RAU/Handover with MME/SGSN change without SGW change procedure, ifthe level of support changes. The MME shall include the ECGI/TAI in theULI, the SGSN shall include the CGUSAI in the ULI. The SGW shall includethis IE on S5/S8 if it receives the ULI from MME/SGSN. Serving Network CThis IE shall be sent on S5/S8 for a TAU with Serving 0 an associatedMME change and the SGW Network change. C This IE shall be included onS5/S8 for a O RAU/Handover with an associated SGSN/MME change and SGWchange. RAT Type C This IE shall be sent on the S11 interface for a RATType 0 TAU with anSGSN interaction, UE triggered Service Request or anI-RAT Handover. This IE shall be sent on the S5/S8 interface for achange of RAT type. This IE shall be sent on the S4 interface for a RAUwith MME interaction, a RAU with an SGSN change, a UE Initiated ServiceRequest or an I-RAT Handover. Indication Flags C This IE shall beincluded if any one of the Indication 0 applicable flags is set to 1.Applicable flags are: ISRAI: This flag shall be used on S4/S11 interfaceand set to 1 if the ISR is established between the MME and the S4 SGSN.Handover Indication: This flag shall be set for an E-UTRAN InitialAttach or for a UE Requested PDN Connectivity, if the UE comes from anon-3GPP access. Direct Tunnel Flag: This flag shall be used on the S4interface and set to 1 if Direct Tunnel is used. Change Reportingsupport Indication: shall be used on S4/S11, S5/S8 and set if theSGSN/MME supports location Info Change Reporting. This flag should beignored by SGW if no message is sent on S5/S8. Change F-TEID supportIndication: This flag shall be used on S4/S11 for an IDLE state UEinitiated TAU/RAU procedure and set to 1 to allow the SGW changing theGTP-U F-TEID. Sender F-TEID C This IE shall be sent on the S11 and S4F-TEID 0 for Control Plane interfaces for a TAU/RAU/Handover withMME/SGSN change and without any SGW change. This IE shall be sent on theS5 and S8 interfaces for a TAU/RAU/Handover with a SGW change. AggregateC The APN-AMBR shall be sent for the PS AMBR 0 Maximum Bit mobility fromthe Gn/Gp SGSN to the S4 Rate (APN- SGSN/MME procedures. AMBR) DelayDownlink C This IE shall be sent on the S11 interface for a Delay Value0 Packet UE triggered Service Request. Notification Request BearerContexts C This IE shall not be sent on the S5/S8 interface BearerContext 0 to be modified for a UE triggered Service Request. WhenHandover Indication flag is set to 1 (i.e., for EUTRAN Initial Attach orUE Requested PDN Connectivity when the UE comes from non-3GPP access),the PGW shall ignore this IE. See NOTE 1 Several IEs with the same typeand instance value may be included as necessary to represent a list ofBearers to be modified. Bearer Contexts C This IE shall be included onthe S4 and S11 Bearer Context 1 to be removed interfaces for theTAU/RAU/Handover and Service Request procedures where any of the bearersexisting before the TAU/RAU/Handover procedure and Service Requestprocedures will be deactivated as consequence of the TAU/RAU/Handoverprocedure and Service Request procedures. For each of those bearers, anIE with the same type and instance value, shall be included. Recovery CThis IE shall be included if contacting the peer Recovery 0 for thefirst time UE Time Zone O This IE may be included by the MME on the UETime Zone 0 S11 interface or by the SGSN on the S4 interface. C If SGWreceives this IE, SGW shall forward it to PGW across S5/S8 interface.MME-FQ-CSID C This IE shall be included by MME on S11 and FQ-CSID 0shall be forwarded by SGW on S5/S8 according to the requirements in 3GPPTS 23.007 [17]. SGW-FQ-CSID C This IE shall be included by SGW on S5/S8FQ-CSID 1 according to the requirements in 3GPP TS 23.007 [17]. MTUSupported C This IE shall be included when the MTU size supported by theeNodeB is larger than the default size of 1500 (value = 0) and may beincluded if the value is 0 (default). This IE shall be included by SGWon S5/S8 whenever present Private Extension O Private VS Extension NOTE1: This requirement is introduced for backwards compatibility reasons.If Bearer Contexts to be modified IE(s) is received in the Modify BearerRequest message, the PGW shall include corresponding Bearer Contextsmodified IE(s) in the Modify Bearer Response message.

The PGW can respond to the modify bearer request by sending a modifybearer response with PCO indicating a new mobile subscriber MTU IPv4 orIPv6 Link MTU value.

The MME would then inform the eNodeB of the selected MTU value in theTAU Accept Message. It can map the MTU size to one of the values definedearlier (e.g., 0 or 1) and comprise the MTU Support IE in the TAU Acceptmessage.

TABLE 4 IEI Information Element Type/Reference Presence Format LengthProtocol discriminator Protocol discriminator M V 1/2 9.2 Securityheader type Security header type M V 1/2 9.3.1 Tracking area updateMessage type M V 1 accept message identity 9.8 EPS update result EPSupdate result M V 1/2 9.9.3.13 Spare half octet Spare half octet M V 1/29.9.2.9  5A T3412 value GPRS timer O TV 2 9.9.3.16 50 GUTI EPS mobileidentity O TLV 13  9.9.3.12 54 TAI list Tracking area identity list OTLV 8-98 9.9.3.33 57 EPS bearer context EPS bearer context status O TLV4 status 9.9.2.1 13 Location area Location area O TV 6 identificationidentification 9.9.2.2 23 MS identity Mobile identity O TLV 7-10 9.9.2.353 EMM cause EMM cause O TV 2 9.9.3.9 17 T3402 value GPRS timer O TV 29.9.3.16 59 T3423 value GPRS timer O TV 2 9.9.3.16  4A Equivalent PLMNsPLMN list O TLV 5-47 9.9.2.8 34 Emergency number list Emergency numberlist O TLV 5-50 9.9.3.37 64 EPS network feature EPS network feature OTLV 3 support support 9.9.3.12A F- Additional update Additional updateresult O TV 1 result 9.9.3.0A  5E T3412 extended value GPRS timer 3 OTLV 3 9.9.3.16B  6A T3324 value GPRS timer 2 O TLV 3 9.9.3.16A  6EExtended DRX Extended DRX O TLV 3 parameters parameters 9.9.3.46 68Header compression Header compression O TLV 4 configuration statusconfiguration status 9.9.4.27 65 DCN-ID DCN-ID O TLV 4 9.9.3.48 ?? MTUSupported See prior explanation O TV 1

If the eNodeB receives a different MTU size than the MTU size itprovided in the TAU request, the eNodeB uses the MTU size it receivesfrom the PGW and should provide that update to the UE. Otherwise theeNodeB defaults to 1500 if the IE is missing.

FIG. 11 illustrates an example, non-limiting, MTU quarantine bandnetwork implementation 1100 in accordance with one or more embodimentsdescribed herein. The introduction of any strategy to have variable MTUnetwork settings coming back to a central routing point (PGW) ischallenging, particularly if that network MTU knowledge is used to setvariable MTU settings on the UE. Having the ability to set variable MTUsettings on the UE, is desired in order to fully realize end-to-end MTUimprovements that can drive increases in data throughput and reductionin latency.

For example, if a network, using PGW PCO options, provides an increasedMTU to a UE in a network that supports a larger MTU design, and thenthat UE travels to a network that supports a lower MTU design, there hasbeen no established method of updating the UE MTU setting. To furtherillustrate this point, refer back to FIG. 6. Suppose a UE authenticatesin an MTU 2000 network which borders a 1500 MTU network. If that UE isprovided a 1930 MTU size, and then drives to the MTU 1500 network, theUE packets will be too large for the 1500 network and will have to befragmented. This fragmentation can reduce throughput and increaselatency, which is undesired. In order to reduce the probability of suchan occurrence, the use of a quarantine guard band is provided herein.

According to an example, GTP fragmentation can cause out of orderpackets if the traffic is of mixed size. As speeds are increased, thenumber of packets between the two fragments can break layer 4 awarenetworking equipment such as firewalls, NAT and load balancers.Increasing buffer size is not practical as speeds are increased to 1Gbps and beyond.

The quarantine guard band operates as an MTU safety zone around networksthat only support lower MTU sizes. For example, a legacy MTU network1102 can support MTU 1500, and is depicted in a first circle in a groupof concentric circles. A second range or a second circle 1104 can beestablished around a geographic area represented by the first circle.The second circle 1104 represents a larger geographic area around thelegacy MTU network 1102. For example, the second circle 1104 canrepresent a range of fifty miles for which the MTU quarantine band willbe active, and represents MTU 1500. Further, a third circle 1106represents an emancipated band that can represent a larger geographicarea (e.g., 1,000 miles). Within the range of the MTU emancipated band(e.g., the third circle 1106), an emancipated MTU network can be capableof a higher MTU size (e.g., MTU 2000).

In further detail, for “X” number of miles surrounding the quarantinednetwork, the UE is still provided the MTU setting of the quarantinednetwork, by the PGW PCO option. This can be accomplished by the eNB, inthe quarantine band, providing the quarantined MTU setting in the MTUsignaling message to the PGW. Therefore, the UE can have the correct MTUsetting if/when the UE is moved to the quarantined network. Returning tothe above example, if the quarantined band was 50 miles, then all of theeNB's within a 50 mile radius of the quarantined network would bestatically provisioned with the 1500 MTU setting, even though they couldbe capable of a 2000 maximum packet size. When a UE authenticates inthis zone, they would be provided a 1430 MTU setting by the PGW. Whenthe UE travels to the MTU 1500 quarantined network, it will have theoptimum MTU setting, and therefore the UE packets will not have to befragmented, and thus subjected to worse network performance.

If the UE, in the quarantined guard band, moves out of the guard bandand goes to the higher MTU network of 2000, the UE will still beprovisioned with the 1430 MTU packet size setting and thus cannotpartake of the higher MTU packet size available in that network, butthat is satisfactory, in order to keep the gains of not fragmenting inthe legacy network. It is a tradeoff that overall reduces the amount ofnetwork fragmentation.

When the UE authenticates in the network emancipation band, that iswhere the end user will see the most gain, as the end user willexperience the most significant increase in throughput and reducedlatency, as the UE can take advantage of the full MTU available in thenetwork emancipation zone. If the UE is moved from the networkemancipation band into the MTU quarantine band, the UE will still keepthe MTU that it authenticated with, and thus fragmentation can occur onits packets while in the MTU quarantine band. It is noted that it cannotbe assumed that the more advanced equipment present in the MTUquarantine band will handle fragmentation better, than if fragmentationwould occur in the legacy MTU network. Some newer equipment can be coststreamlined and be challenged by fragmentation, just as severely asolder equipment. Adjustment of the size and location of the MTUquarantine band, could be adjusted, based on network conditions, toprotect any equipment, either old or new, that is being challenged byexcessive GTP packet fragmentation.

According to an alternative or additional implementation, if the MTUsize is not compatible, the data session can be terminated and a newdata session started. In some implementations, handoffs betweenincompatible MTU sized transports can be prevented or not supported.

FIG. 12 illustrates an example, non-limiting, method for utilization ofa flexible transmission unit packet core design in accordance with oneor more embodiments described herein. Repetitive description of likeelements employed in other embodiments described herein is omitted forsake of brevity. The method 1200 can be implemented by a network deviceof a wireless network, the network device comprising a processor.Alternatively, or additionally, a machine-readable storage medium cancomprise executable instructions that, when executed by a processor,facilitate performance of operations for the method 1200.

At 1202, a first transmission unit setting can be received from a firstnetwork device. The first transmission unit setting can indicate a firstsize of a first largest network layer protocol data unit that can becommunicated in a first single network transaction by the first networkdevice. According to an example, receiving the first size can comprisereceiving the first size in a general packet radio service tunnelingprotocol user data tunneling header that comprises an extension header.A first internal configuration (e.g., a data table) associated with thefirst network device can be set, at 1204, to the first transmission unitsetting.

A second transmission unit setting can be received from a second networkdevice at 1206. The second transmission unit setting can indicate asecond size of a second largest network layer protocol data unit thatcan be communicated in a second single network transaction by the secondnetwork device. The first size can be different from the second size.Further, at 1208, a second internal configuration associated with thesecond network device can be set to the second transmission unitsetting.

According to an implementation, the method can comprise determining athird size that represents the size of a transmission packet intendedfor a user equipment device in communication with the first networkdevice. The third size can be less than the first size. Further to thisimplementation, the method can comprise facilitating a transmission ofan indication of the third size and an identification of the userequipment device to the first network device. In an example, determiningthe third size can comprise determining an amount of overhead loss thatoccurs on a data plane path between the first network device and theuser equipment device and reducing the first size by the amount ofoverhead loss.

According to an example, provided herein is a method of sending a staticMTU setting to a centralized router and have that router dynamicallyassociate the MTU capabilities of the edge part of the network. Inanother example, multiple MTU settings can be allowed on a single sourceIP address. In yet another example, “MTU advertising” of a source IPaddress MTU setting to destination IP addresses can be allowed.According to another example, provided is a method of broadcasting thelocal source IP address to advertise its MTU setting to all destinationIP addresses, or to select few destination IP addresses, based on alocal data structure that determines which destination IP addressesshould get the MTU messages. In some examples provided is a method bywhich an end user, is provided an MTU setting, based on knowledge of thepacket delivery limitations of the data plane path to it. Further,timeout values for PGW logic MTU data structure are provided herein. Inaddition, initial MTU default values on PGW data structure if source IPaddress is not in logical MTU data structure can be facilitated. In yetanother example, MTU network updates as a mobile session IRATs from oneMTU zone to another one that has a different MTU setting can also befacilitated with the disclosed aspects.

According to some implementations, the method can comprise populating alogical transmission unit data structure with a first capability of thefirst network device and a second capability of the second networkdevice. Further, in the logical transmission unit data structure thefirst capability can be correlated to the first network device based ona first source internet protocol address of the first network device,and the second capability can be correlated to the second network devicebased on a second source internet protocol address of the second networkdevice.

In accordance with an additional implementation, the method can compriseimplementing a first quarantine band within a first geographic radius ofthe first network device, wherein the first quarantine band specifies athird transmission unit setting within the first quarantine band to beequal to the first size. Further to this additional implementation, themethod can comprise implementing a second quarantine band within asecond geographic radius of the first network device, wherein the secondquarantine band specifies a fourth transmission unit setting within thefirst quarantine band to be equal to a third size which is a highertransmission unit setting than the first size.

The term “mobile device” can be interchangeable with (or include) a userequipment (UE) or other terminology. Mobile device (or user equipment)refers to any type of wireless device that communicates with a radionetwork node in a cellular or mobile communication system. Examples ofUEs include, but are not limited to, a target device, a device to device(D2D) UE, a machine type UE or a UE capable of machine to machine (M2M)communication, a Personal Digital Assistant (PDA), a tablet, a mobileterminal, a smart phone, a laptop embedded equipment (LEE), a laptopmounted equipment (LME), a Universal Serial Bus (USB) dongle, and so on.

As used herein, the term “network device” can be interchangeable with(or include) a network, a network controller or any number of othernetwork components. Further, as utilized herein, the non-limiting termradio network node, or simply network node (e.g., network device,network node device) is used herein to refer to any type of network nodeserving communication devices and/or connected to other network nodes,network elements, or another network node from which the communicationdevices can receive a radio signal. In cellular radio access networks(e.g., universal mobile telecommunications system (UMTS) networks),network devices can be referred to as base transceiver stations (BTS),radio base station, radio network nodes, base stations, NodeB, eNodeB(e.g., evolved NodeB), and so on. In 5G terminology, the network nodescan be referred to as gNodeB (e.g., gNB) devices. Network devices canalso comprise multiple antennas for performing various transmissionoperations (e.g., Multiple Input Multiple Output (MIMO) operations). Anetwork node can comprise a cabinet and other protected enclosures, anantenna mast, and actual antennas. Network devices can serve severalcells, also called sectors, depending on the configuration and type ofantenna. Examples of network nodes or radio network nodes (e.g., thenetwork device 102) can include but are not limited to: NodeB devices,base station (BS) devices, access point (AP) devices, TRPs, and radioaccess network (RAN) devices. The network nodes can also includemulti-standard radio (MSR) radio node devices, comprising: an MSR BS, agNodeB, an eNode B, a network controller, a radio network controller(RNC), a base station controller (BSC), a relay, a donor nodecontrolling relay, a base transceiver station (BTS), an access point(AP), a transmission point, a transmission node, a Remote Radio Unit(RRU), a Remote Radio Head (RRH), nodes in distributed antenna system(DAS), and the like.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate semi-open loopbased transmission diversity for uplink transmissions for a 5G network.Facilitating semi-open loop based transmission diversity for uplinktransmissions in a 5G network can be implemented in connection with anytype of device with a connection to the communication network (e.g., amobile handset, a computer, a handheld device, etc.) any Internet ofthings (IoT) device (e.g., toaster, coffee maker, blinds, music players,speakers, etc.), and/or any connected vehicles (cars, airplanes, spacerockets, and/or other at least partially automated vehicles (e.g.,drones)). In some embodiments, the non-limiting term User Equipment (UE)is used. It can refer to any type of wireless device that communicateswith a radio network node in a cellular or mobile communication system.Examples of UE are target device, device to device (D2D) UE, machinetype UE or UE capable of machine to machine (M2M) communication, PDA,Tablet, mobile terminals, smart phone, Laptop Embedded Equipped (LEE),laptop mounted equipment (LME), USB dongles etc. Note that the termselement, elements and antenna ports can be interchangeably used butcarry the same meaning in this disclosure. The embodiments areapplicable to single carrier as well as to Multi-Carrier (MC) or CarrierAggregation (CA) operation of the UE. The term Carrier Aggregation (CA)is also called (e.g., interchangeably called) “multi-carrier system,”“multi-cell operation,” “multi-carrier operation,” “multi-carrier”transmission and/or reception.

In some embodiments, the non-limiting term radio network node or simplynetwork node is used. It can refer to any type of network node thatserves one or more UEs and/or that is coupled to other network nodes ornetwork elements or any radio node from where the one or more UEsreceive a signal. Examples of radio network nodes are Node B, BaseStation (BS), Multi-Standard Radio (MSR) node such as MSR BS, eNode B,network controller, Radio Network Controller (RNC), Base StationController (BSC), relay, donor node controlling relay, Base TransceiverStation (BTS), Access Point (AP), transmission points, transmissionnodes, RRU, RRH, nodes in Distributed Antenna System (DAS) etc.

Cloud Radio Access Networks (RAN) can enable the implementation ofconcepts such as Software-Defined Network (SDN) and Network FunctionVirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openApplication Programming Interfaces (APIs) and move the network coretowards an all Internet Protocol (IP), cloud based, and software driventelecommunications network. The SDN controller can work with, or takethe place of Policy and Charging Rules Function (PCRF) network elementsso that policies such as quality of service and traffic management androuting can be synchronized and managed end to end.

To meet the huge demand for data centric applications, 4G standards canbe applied to 5G, also called New Radio (NR) access. 5G networks cancomprise the following: data rates of several tens of megabits persecond supported for tens of thousands of users; 1 gigabit per secondcan be offered simultaneously (or concurrently) to tens of workers onthe same office floor; several hundreds of thousands of simultaneous (orconcurrent) connections can be supported for massive sensor deployments;spectral efficiency can be enhanced compared to 4G; improved coverage;enhanced signaling efficiency; and reduced latency compared to LTE. Inmulticarrier system such as OFDM, each subcarrier can occupy bandwidth(e.g., subcarrier spacing). If the carriers use the same bandwidthspacing, then it can be considered a single numerology. However, if thecarriers occupy different bandwidth and/or spacing, then it can beconsidered a multiple numerology.

The various aspects described herein can relate to new radio, which canbe deployed as a standalone radio access technology or as anon-standalone radio access technology assisted by another radio accesstechnology, such as Long Term Evolution (LTE), for example. It should benoted that although various aspects and embodiments have been describedherein in the context of 5G, Universal Mobile Telecommunications System(UMTS), and/or LTE, or other next generation networks, the disclosedaspects are not limited to 5G, a UMTS implementation, and/or an LTEimplementation as the techniques can also be applied in 3G, 4G, or LTEsystems. For example, aspects or features of the disclosed embodimentscan be exploited in substantially any wireless communication technology.Such wireless communication technologies can include UMTS, Code DivisionMultiple Access (CDMA), Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS,Third Generation Partnership Project (3GPP), LTE, Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High SpeedPacket Access (HSPA), Evolved High Speed Packet Access (HSPA+),High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink PacketAccess (HSUPA), Zigbee, or another IEEE 802.XX technology. Additionally,substantially all aspects disclosed herein can be exploited in legacytelecommunication technologies. Further, the various aspects can beutilized with any Radio Access Technology (RAT) or multi-RAT systemwhere the mobile device operates using multiple carriers (e.g., LTEFrequency Division Duplexing (FDD)/Time-Division Duplexing (TDD),Wideband Code Division Multiplexing Access (WCMDA)/HSPA, Global Systemfor Mobile Communications (GSM)/GSM EDGE Radio Access Network (GERAN),Wi Fi, Wireless Local Area Network (WLAN), WiMax, CDMA2000, and so on).

As used herein, “5G” can also be referred to as New Radio (NR) access.Accordingly, systems, methods, and/or machine-readable storage media forfacilitating improvements to the uplink performance for 5G systems aredesired. As used herein, one or more aspects of a 5G network cancomprise, but is not limited to, data rates of several tens of megabitsper second (Mbps) supported for tens of thousands of users; at least onegigabit per second (Gbps) to be offered simultaneously to tens of users(e.g., tens of workers on the same office floor); several hundreds ofthousands of simultaneous connections supported for massive sensordeployments; spectral efficiency significantly enhanced compared to 4G;improvement in coverage relative to 4G; signaling efficiency enhancedcompared to 4G; and/or latency significantly reduced compared to LTE.

Referring now to FIG. 13, illustrated is an example block diagram of anexample mobile handset 1300 operable to engage in a system architecturethat facilitates wireless communications according to one or moreembodiments described herein. Although a mobile handset is illustratedherein, it will be understood that other devices can be a mobile device,and that the mobile handset is merely illustrated to provide context forthe embodiments of the various embodiments described herein. Thefollowing discussion is intended to provide a brief, general descriptionof an example of a suitable environment in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, solid statedrive (SSD) or other solid-state storage technology, Compact Disk ReadOnly Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer. In this regard, the terms “tangible” or “non-transitory”herein as applied to storage, memory or computer-readable media, are tobe understood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset includes a processor 1302 for controlling and processing allonboard operations and functions. A memory 1304 interfaces to theprocessor 1302 for storage of data and one or more applications 1306(e.g., a video player software, user feedback component software, etc.).Other applications can include voice recognition of predetermined voicecommands that facilitate initiation of the user feedback signals. Theapplications 1306 can be stored in the memory 1304 and/or in a firmware1308, and executed by the processor 1302 from either or both the memory1304 or/and the firmware 1308. The firmware 1308 can also store startupcode for execution in initializing the handset 1300. A communicationscomponent 1310 interfaces to the processor 1302 to facilitatewired/wireless communication with external systems, e.g., cellularnetworks, VoIP networks, and so on. Here, the communications component1310 can also include a suitable cellular transceiver 1311 (e.g., a GSMtransceiver) and/or an unlicensed transceiver 1313 (e.g., Wi-Fi, WiMax)for corresponding signal communications. The handset 1300 can be adevice such as a cellular telephone, a PDA with mobile communicationscapabilities, and messaging-centric devices. The communicationscomponent 1310 also facilitates communications reception fromterrestrial radio networks (e.g., broadcast), digital satellite radionetworks, and Internet-based radio services networks.

The handset 1300 includes a display 1312 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1312 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1312 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1314 is provided in communication with the processor 1302 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 1300, for example. Audio capabilities areprovided with an audio I/O component 1316, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 1316 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 1300 can include a slot interface 1318 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 1320, and interfacingthe SIM card 1320 with the processor 1302. However, it is to beappreciated that the SIM card 1320 can be manufactured into the handset1300, and updated by downloading data and software.

The handset 1300 can process IP data traffic through the communicationscomponent 1310 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 1300 and IP-based multimediacontent can be received in either an encoded or a decoded format.

A video processing component 1322 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1322can aid in facilitating the generation, editing, and sharing of videoquotes. The handset 1300 also includes a power source 1324 in the formof batteries and/or an AC power subsystem, which power source 1324 caninterface to an external power system or charging equipment (not shown)by a power I/O component 1326.

The handset 1300 can also include a video component 1330 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 1330 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1332 facilitates geographically locating the handset 1300. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 1334facilitates the user initiating the quality feedback signal. The userinput component 1334 can also facilitate the generation, editing andsharing of video quotes. The user input component 1334 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1306, a hysteresis component 1336facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1338 can be provided that facilitatestriggering of the hysteresis component 1336 when the Wi-Fi transceiver1313 detects the beacon of the access point. A SIP client 1340 enablesthe handset 1300 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 1306 can also include aclient 1342 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 1300, as indicated above related to the communicationscomponent 1310, includes an indoor network radio transceiver 1313 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 1300. The handset 1300 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 14, illustrated is an example block diagram of anexample computer 1400 operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein. The computer 1400 can provide networking andcommunication capabilities between a wired or wireless communicationnetwork and a server (e.g., Microsoft server) and/or communicationdevice. In order to provide additional context for various aspectsthereof, FIG. 14 and the following discussion are intended to provide abrief, general description of a suitable computing environment in whichthe various aspects of the innovation can be implemented to facilitatethe establishment of a transaction between an entity and a third party.While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the innovation also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the innovation can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules, or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 14, implementing various aspects described hereinwith regards to the end-user device can include a computer 1400, thecomputer 1400 including a processing unit 1404, a system memory 1406 anda system bus 1408. The system bus 1408 couples system componentsincluding, but not limited to, the system memory 1406 to the processingunit 1404. The processing unit 1404 can be any of various commerciallyavailable processors. Dual microprocessors and other multi processorarchitectures can also be employed as the processing unit 1404.

The system bus 1408 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1406includes read-only memory (ROM) 1427 and random access memory (RAM)1412. A basic input/output system (BIOS) is stored in a non-volatilememory 1427 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1400, such as during start-up. The RAM 1412 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1400 further includes an internal hard disk drive (HDD)1414 (e.g., EIDE, SATA), which internal hard disk drive 1414 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1416, (e.g., to read from or write to aremovable diskette 1418) and an optical disk drive 1420, (e.g., readinga CD-ROM disk 1422 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1414, magnetic diskdrive 1416 and optical disk drive 1420 can be connected to the systembus 1408 by a hard disk drive interface 1424, a magnetic disk driveinterface 1426 and an optical drive interface 1428, respectively. Theinterface 1424 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject innovation.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1400 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1400, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the exemplary operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed innovation.

A number of program modules can be stored in the drives and RAM 1412,including an operating system 1430, one or more application programs1432, other program modules 1434 and program data 1436. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1412. It is to be appreciated that the innovation canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1400 throughone or more wired/wireless input devices, e.g., a keyboard 1438 and apointing device, such as a mouse 1440. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1404 through an input deviceinterface 1442 that is coupled to the system bus 1408, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1444 or other type of display device is also connected to thesystem bus 1408 through an interface, such as a video adapter 1446. Inaddition to the monitor 1444, a computer 1400 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1400 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1448. The remotecomputer(s) 1448 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 1450 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1452 and/or larger networks,e.g., a wide area network (WAN) 1454. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which canconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1400 isconnected to the local network 1452 through a wired and/or wirelesscommunication network interface or adapter 1456. The adapter 1456 canfacilitate wired or wireless communication to the LAN 1452, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1456.

When used in a WAN networking environment, the computer 1400 can includea modem 1458, or is connected to a communications server on the WAN1454, or has other means for establishing communications over the WAN1454, such as by way of the Internet. The modem 1458, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1408 through the input device interface 1442. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1450. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, in a hotel room, or a conference room at work, withoutwires. Wi-Fi is a wireless technology similar to that used in a cellphone that enables such devices, e.g., computers, to send and receivedata indoors and out; anywhere within the range of a base station. Wi-Finetworks use radio technologies called IEEE 802.11 (a, b, g, etc.) toprovide secure, reliable, fast wireless connectivity. A Wi-Fi networkcan be used to connect computers to each other, to the Internet, and towired networks (which use IEEE 802.3 or Ethernet). Wi-Fi networksoperate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps(802.11a) or 54 Mbps (802.11b) data rate, for example, or with productsthat contain both bands (dual band), so the networks can providereal-world performance similar to the basic 10BaseT wired Ethernetnetworks used in many offices.

An aspect of 5G, which differentiates from previous 4G systems, is theuse of NR. NR architecture can be designed to support multipledeployment cases for independent configuration of resources used forRACH procedures. Since the NR can provide additional services than thoseprovided by LTE, efficiencies can be generated by leveraging the prosand cons of LTE and NR to facilitate the interplay between LTE and NR,as discussed herein.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics can be combined in any suitable manner in one or moreembodiments.

As used in this disclosure, in some embodiments, the terms “component,”“system,” “interface,” and the like are intended to refer to, orcomprise, a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution, and/or firmware. As anexample, a component can be, but is not limited to being, a processrunning on a processor, a processor, an object, an executable, a threadof execution, computer-executable instructions, a program, and/or acomputer. By way of illustration and not limitation, both an applicationrunning on a server and the server can be a component.

One or more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components can communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software application orfirmware application executed by one or more processors, wherein theprocessor can be internal or external to the apparatus and can executeat least a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can comprise a processor therein to executesoftware or firmware that confer(s) at least in part the functionalityof the electronic components. In an aspect, a component can emulate anelectronic component via a virtual machine, e.g., within a cloudcomputing system. While various components have been illustrated asseparate components, it will be appreciated that multiple components canbe implemented as a single component, or a single component can beimplemented as multiple components, without departing from exampleembodiments.

In addition, the words “example” and “exemplary” are used herein to meanserving as an instance or illustration. Any embodiment or designdescribed herein as “example” or “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments ordesigns. Rather, use of the word example or exemplary is intended topresent concepts in a concrete fashion. As used in this application, theterm “or” is intended to mean an inclusive “or” rather than an exclusive“or.” That is, unless specified otherwise or clear from context, “Xemploys A or B” is intended to mean any of the natural inclusivepermutations. That is, if X employs A; X employs B; or X employs both Aand B, then “X employs A or B” is satisfied under any of the foregoinginstances. In addition, the articles “a” and “an” as used in thisapplication and the appended claims should generally be construed tomean “one or more” unless specified otherwise or clear from context tobe directed to a singular form.

Moreover, terms such as “mobile device equipment,” “mobile station,”“mobile,” subscriber station,” “access terminal,” “terminal,” “handset,”“communication device,” “mobile device” (and/or terms representingsimilar terminology) can refer to a wireless device utilized by asubscriber or mobile device of a wireless communication service toreceive or convey data, control, voice, video, sound, gaming orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably herein and with reference to the relateddrawings. Likewise, the terms “access point (AP),” “Base Station (BS),”BS transceiver, BS device, cell site, cell site device, “Node B (NB),”“evolved Node B (eNode B),” “home Node B (HNB)” and the like, areutilized interchangeably in the application, and refer to a wirelessnetwork component or appliance that transmits and/or receives data,control, voice, video, sound, gaming or substantially any data-stream orsignaling-stream from one or more subscriber stations. Data andsignaling streams can be packetized or frame-based flows.

Furthermore, the terms “device,” “communication device,” “mobiledevice,” “subscriber,” “customer entity,” “consumer,” “customer entity,”“entity” and the like are employed interchangeably throughout, unlesscontext warrants particular distinctions among the terms. It should beappreciated that such terms can refer to human entities or automatedcomponents supported through artificial intelligence (e.g., a capacityto make inference based on complex mathematical formalisms), which canprovide simulated vision, sound recognition and so forth.

Embodiments described herein can be exploited in substantially anywireless communication technology, comprising, but not limited to,wireless fidelity (Wi-Fi), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), worldwideinteroperability for microwave access (WiMAX), enhanced general packetradio service (enhanced GPRS), third generation partnership project(3GPP) long term evolution (LTE), third generation partnership project 2(3GPP2) ultra mobile broadband (UMB), high speed packet access (HSPA),Z-Wave, Zigbee and other 802.XX wireless technologies and/or legacytelecommunication technologies.

Systems, methods and/or machine-readable storage media for facilitatinga two-stage downlink control channel for 5G systems are provided herein.Legacy wireless systems such as LTE, Long-Term Evolution Advanced(LTE-A), High Speed Packet Access (HSPA) etc. use fixed modulationformat for downlink control channels. Fixed modulation format impliesthat the downlink control channel format is always encoded with a singletype of modulation (e.g., quadrature phase shift keying (QPSK)) and hasa fixed code rate. Moreover, the forward error correction (FEC) encoderuses a single, fixed mother code rate of 1/3 with rate matching. Thisdesign does not take into the account channel statistics. For example,if the channel from the BS device to the mobile device is very good, thecontrol channel cannot use this information to adjust the modulation,code rate, thereby unnecessarily allocating power on the controlchannel. Similarly, if the channel from the BS to the mobile device ispoor, then there is a probability that the mobile device might not ableto decode the information received with only the fixed modulation andcode rate. As used herein, the term “infer” or “inference” refersgenerally to the process of reasoning about, or inferring states of, thesystem, environment, user, and/or intent from a set of observations ascaptured via events and/or data. Captured data and events can includeuser data, device data, environment data, data from sensors, sensordata, application data, implicit data, explicit data, etc. Inference canbe employed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, machine-readable media,computer-readable (or machine-readable) storage/communication media. Forexample, computer-readable media can comprise, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media. Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope or spirit of the variousembodiments.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the subject matter has been described herein inconnection with various embodiments and corresponding FIGs, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A method, comprising: receiving, by a devicecomprising a processor, a first signal in a general packet radio servicetunneling protocol user data tunneling header that comprises anextension header, wherein the first signal comprises a first value thatrepresents a first transmission unit setting supported by a firstnetwork device, wherein the receiving of the first signal comprisesreceiving a broadcast message from the first network device, thebroadcast message comprises a local source internet protocol address ofthe first network device and is transmitted to a group of destinationinternet protocol addresses, comprising a destination internet protocoladdress of the device; and facilitating, by the device, a firsttransmission of a first group of packets to the first network devicebased on the first value and a second transmission of a second group ofpackets to a second network device based on a second value, wherein thesecond value represents a second transmission unit setting supported bythe second network device.
 2. The method of claim 1, further comprising:prior to the facilitating of the first transmission, receiving, by thedevice, a second signal that comprises the second value, wherein thefirst signal is received from the first network device, and wherein thesecond signal is received from the second network device.
 3. The methodof claim 1, further comprising: prior to the facilitating of the firsttransmission and the second transmission, setting, by the device, aconfiguration of the first network device to the first transmission unitsetting indicated in the first signal, wherein the facilitating of thefirst transmission comprises facilitating the first transmission usingthe first transmission unit setting, and wherein the facilitating of thesecond transmission comprises facilitating the second transmission usingthe second transmission unit setting different from the firsttransmission unit setting.
 4. The method of claim 3, wherein the firstnetwork device is a base station device and the device is a packetgateway device, wherein the receiving of the first signal comprisesreceiving the first transmission unit setting from the base stationdevice, and wherein the setting of the configuration of the firstnetwork device comprises updating the packet gateway device based on thefirst transmission unit setting from the base station device.
 5. Themethod of claim 1, wherein the facilitating of the first transmission ofthe first group of packets to the first network device comprisesfragmenting first communication packets of the first group of packets tosatisfy the first transmission unit setting, and wherein thefacilitating of the second transmission of the second group of packetsto the second network device comprises fragmenting second communicationpackets of the second group of packets to satisfy the secondtransmission unit setting.
 6. The method of claim 1, wherein the deviceis a packet gateway device, wherein the first network device is acontroller device, and wherein the receiving of the first signal fromthe first network device comprises periodically receiving a static file,from the controller device, that comprises the first transmission unitsetting.
 7. The method of claim 1, further comprising: removing, by thedevice, the local source internet protocol address of the first networkdevice from a transmission unit logic data structure based on adetermination that a defined time has elapsed since receipt of the firsttransmission unit setting from the first network device.
 8. The methodof claim 1, further comprising: determining, by the device, a thirdtransmission unit setting for a user equipment serviced by the firstnetwork device; and facilitating, by the device, a configuration of atransmission to the user equipment based on the third transmission unitsetting.
 9. The method of claim 1, wherein the first transmission unitsetting is different than a defined transmission unit setting that iscommon to the first network device and the second network device.
 10. Asystem, comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: determining a first size thatrepresents a size of a transmission packet intended for a user equipmentin communication with a first network device, wherein a second sizerepresents a first largest network layer protocol data unit that is ableto be communicated in a first single network transaction by the firstnetwork device, wherein the first size is less than the second size,wherein the determining comprises: determining an amount of overheadloss that occurs on a data plane path between the first network deviceand the user equipment, and reducing the second size by the amount ofoverhead loss; and transmitting an indication of the first size and anidentification of the user equipment to the first network device. 11.The system of claim 10, wherein the operations further comprise: priorto the determining of the first size, receiving the second size from thefirst network device in a general packet radio service tunnelingprotocol user data tunneling header that comprises an extension header.12. The system of claim 10, wherein the operations further comprise:implementing a first quarantine band within a first geographic radius ofthe first network device, wherein the first quarantine band specifies afirst transmission unit setting within the first quarantine band to beequal to the second size; and implementing a second quarantine bandwithin a second geographic radius of the first network device, whereinthe second quarantine band specifies a second transmission unit settingthat is within the first quarantine band to be equal to the first sizeand that is a higher transmission unit setting than the second size. 13.The system of claim 10, wherein the operations further comprise:populating a logical transmission unit data structure with a firstcapability of the first network device; and correlating, in the logicaltransmission unit data structure, the first capability to the firstnetwork device based on a first source internet protocol address of thefirst network device.
 14. A non-transitory machine-readable medium,comprising executable instructions that, when executed by a processor offirst network equipment, facilitate performance of operations,comprising: receiving a first signal in a general packet radio servicetunneling protocol user data tunneling header that comprises anextension header, wherein the first signal comprises a first value thatrepresents a first transmission unit setting from second networkequipment, wherein the receiving comprises receiving a broadcast messagefrom the second network equipment; and wherein the broadcast messagecomprises a local source internet protocol address of the second networkequipment and is transmitted to a group of destination internet protocoladdresses, comprising a destination internet protocol address of a userequipment; and sending first communication packets to the second networkequipment based on the first value, and second communication packets tothird network equipment based on a second value, wherein the secondvalue represents a second transmission unit setting supported by thethird network equipment.
 15. The non-transitory machine-readable mediumof claim 14, wherein the first transmission unit setting indicates asize of a largest network layer protocol data unit that is able to becommunicated in a single network transaction by the second networkequipment.
 16. The non-transitory machine-readable medium of claim 14,wherein the sending the communication packets to the second networkequipment comprises fragmenting the communication packets to satisfy thefirst transmission unit setting.
 17. The non-transitory machine-readablemedium of claim 14, wherein the group of destination internet protocoladdresses are selected from a local data structure that indicatesrecipients of the broadcast message.
 18. The non-transitorymachine-readable medium of claim 14, wherein the operations furthercomprise: removing the local source internet protocol address of thesecond network equipment from a transmission unit logic data structurebased on a determination that a defined time has elapsed since receiptof the first transmission unit setting from the second networkequipment.
 19. The non-transitory machine-readable medium of claim 14,wherein the second network equipment is a base station device and thefirst network equipment is a packet gateway device, wherein thereceiving of the first signal comprises receiving the first transmissionunit setting from the base station device, and wherein setting aconfiguration of the second network equipment comprises updating thepacket gateway device based on the first transmission unit setting fromthe base station device.
 20. The non-transitory machine-readable mediumof claim 14, wherein the first network equipment is a packet gatewaydevice, wherein the second network equipment is a controller device, andwherein the receiving of the first signal comprises periodicallyreceiving a static file, from the controller device, that comprises thefirst transmission unit setting.